chore: trim issue templates#4656
Merged
Merged
Conversation
- Drop the Priority dropdown from feature-template.yaml and task-template.yaml. Priority is now tracked on the issue itself via GitHub's native field, so the in-template dropdown is redundant. (bug-template.yaml never had one.) - bug-template.yaml: replace the Version dropdown (1.1.0-incubating (Pre-release/Master) | 1.0.0) with a Branch dropdown (main | 1.1.0-incubating). Bugs are reported against branches more often than tagged releases. - task-template.yaml: tighten the Task Type options. Drop "Code Implementation" (every task is code) and add Performance + Other. Final list: Refactor / Cleanup, DevOps / Deployment / CI, Testing / QA, Documentation, Performance, Other. Closes apache#4655 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Yicong-Huang
added
the
release/v1.1.0-incubating
github-actions Bot
pushed a commit
that referenced
this pull request
May 2, 2026
### What changes were proposed in this PR? - Drop the **Priority** dropdown from `feature-template.yaml` and `task-template.yaml`. Priority is tracked on the issue itself via GitHub's native field, so the in-template dropdown is redundant. `bug-template.yaml` never had one. - `bug-template.yaml`: replace the **Version** dropdown (`1.1.0-incubating (Pre-release/Master)` / `1.0.0`) with a **Branch** dropdown (`main` / `1.1.0-incubating`). Bugs are reported against branches more often than tagged releases. - `task-template.yaml`: tighten **Task Type**. Drop "Code Implementation" (every task is code) and add Performance + Other. Final list: Refactor / Cleanup, DevOps / Deployment / CI, Testing / QA, Documentation, Performance, Other. No other field changes. ### Any related issues, documentation, discussions? Closes #4655 ### How was this PR tested? YAML parses locally for all three templates. Real-world test: open the "New issue" UI and confirm the dropdowns/labels render as expected once merged. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> (backported from commit 592e6a3)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
feature-template.yamlandtask-template.yaml. Priority is tracked on the issue itself via GitHub's native field, so the in-template dropdown is redundant.bug-template.yamlnever had one.bug-template.yaml: replace the Version dropdown (1.1.0-incubating (Pre-release/Master)/1.0.0) with a Branch dropdown (main/1.1.0-incubating). Bugs are reported against branches more often than tagged releases.task-template.yaml: tighten Task Type. Drop "Code Implementation" (every task is code) and add Performance + Other. Final list: Refactor / Cleanup, DevOps / Deployment / CI, Testing / QA, Documentation, Performance, Other.No other field changes.
Any related issues, documentation, discussions?
Closes #4655
How was this PR tested?
YAML parses locally for all three templates. Real-world test: open the "New issue" UI and confirm the dropdowns/labels render as expected once merged.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7)